chore(deps): update dependency jsdom to v27 #216
+212
−166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^22.1.0->^27.0.1Release Notes
jsdom/jsdom (jsdom)
v27.0.1Compare Source
class=""attribute changes is only possible with a new version of jsdom. (asamuzaK)v27.0.0Compare Source
Changes since 26.1.0
BeforeUnloadEvent,BlobEvent,DeviceMotionEvent(omittingrequestPermission()),DeviceOrientationEvent(omittingrequestPermission()),PointerEvent,PromiseRejectionEvent, andTransitionEvent.movementXandmovementYtoMouseEvent. (These are from the Pointer Lock specification, the rest of which is not implemented.)customElements.getName(). (mash-graz)"jsdomError"events are now documented, with specifictypeproperties and other properties that depend on the type.sendTo()was renamed toforwardTo().jsdomErrorsoption toforwardTo()can be used to control which errors are sent to the Node.js console. This replaces the previousomitJSDOMErrorsboolean option."jsdomError"s for failedXMLHttpRequestfetches are no longer emitted."jsdomError"s to the Node.js console are streamlined.nwsapito@asamuzakjp/dom-selector, closing over 20 selector-related bugs.tough-cookie, which now considers URLs likehttp://localhost/to be secure contexts (per the spec), and thus will returnSecure-flagged cookies for such URLs. (colincasey)cssstyle, which brings along many improvements and fixes to theCSSStyleDeclarationobject and its properties.element.click()to fire aPointerEventinstead of aMouseEvent.<input>element'spattern=""attribute to use thevregular expression flag, instead ofu.Windowobject, including named properties and changing various data properties to accessor properties.document.createEvent()to accept a more correct set of event names.ElementInternalsaccessibility getters and setters. (They were introduced in v23.1.0, but due to inadequate test coverage never actually worked.)Object.defineProperty()on certain objects, such asHTMLSelectElementinstances.jsdom.reconfigure({ url })not updatingdocument.baseURIor properties derived from it. (This regressed in v26.1.0.)initial,inherit, andunsetkeywords, to resolve correctly. (asamuzaK)displaystyle resolution. (asamuzaK)Changes since 27.0.0-beta.3
cssstyle, which brings along various CSS parsing fixes.v26.1.0Compare Source
<defs>(SVGDefsElement),<desc>(SVGDescElement),<g>(SVGGElement),<metadata>(SVGMetadataElement),<switch>(SVGSwitchElement), and<symbol>(SVGSymbolElement).SVGAnimatedPreserveAspectRatioandSVGAnimatedRect, including support in the reflection layer.SVGSVGElementcreateSVGRect()method, and theSVGRecttype (which is distinct fromDOMRect.)HTMLFormElement.SVGElementviewportElement()method to correctly establish the viewport based on ancestor elements.form-datadependency in favor of our own smaller implementation ofmultipart/form-dataserialization. No functional changes are expected.v26.0.0Compare Source
Breaking change:
canvaspeer dependency requirement has been upgraded from v2 to v3. (sebastianwachter)Other changes:
AbortSignal.any(). (jdbevan)ElementInternalslabelsproperty. The form-associated callbacks are not yet supported. (hesxenon)whatwg-url, adding support forURL.parse().cssstyleandrrweb-cssom, to improve CSS parsing capabilities.nwsapi, improving CSS selector matching.parse5, fixing a bug around<noframes>elements and HTML entity decoding.JSDOM.fromURL()to properly reject the returned promise if the server redirects to an invalid URL, instead of causing an uncaught exception.v25.0.1Compare Source
tough-cookie, which no longer prints a deprecation warning.v25.0.0Compare Source
This major release changes the prototype of a jsdom's
EventTarget.prototypeto point to theObject.prototypeinside the jsdom, instead of pointing to the Node.jsObject.prototype. Thus, the prototype chain ofWindowstays entirely within the jsdom, never crossing over into the Node.js realm.This only occurs when
runScriptsis set to non-default values of"dangerously"or"outside-only", as with the default value, there is no separateObject.prototypeinside the jsdom.This will likely not impact many programs, but could cause some changes in
instanceofbehavior, and so out of an abundance of caution, we're releasing it as a new major version.v24.1.3Compare Source
postMessage()that were done as a bare property (i.e.,postMessage()instead ofwindow.postMessage()).v24.1.2Compare Source
inoperator applied toEventTargetmethods, e.g.'addEventListener' in window, which only appeared in Node.js ≥22.5.0. (legendecas)blur(): it no longer firesfocusandfocusinon theDocument, andblurandfocusoutno longer have theirrelatedTargetproperty set. (asamuzaK)v24.1.1Compare Source
selectionchangeevent on theDocumentobject. (piotr-oles)v24.1.0Compare Source
getSetCookie()method to theHeadersclass. (ushiboy)Object.prototype, like"constructor"or"toString".rweb-cssom, which can now parse additional CSS constructs.v24.0.0Compare Source
This release reverts our selector engine back to
nwsapi. As discussed in #3659, the performance regressions from@asamuzakjp/dom-selectorturned out to be higher than anticipated. In the future, we can revisit@asamuzakjp/dom-selectorafter it reachesnwsapi's performance on the two real-world benchmarks provided by the community.Since reverting to
nwsapicauses several functionality regressions, e.g. removing:has()support, we've decided to make this a major version.Additionally:
input.maxLength,input.minLength,input.size,progress.max,tableCell.colSpan,tableCell.rowSpan,tableCol.span,textArea.cols,textArea.maxLength,textArea.minLength,textArea.rows.v23.2.0Compare Source
This release switches our CSS selector engine from
nwsapito@asamuzakjp/dom-selector. The new engine is more actively maintained, and supports many new selectors: see the package's documentation for the full list. It also works better with shadow trees.There is a potential of a performance regression due to this change. In our stress test benchmark, which runs most of these 273 selectors against this 128 KiB document, the new engine completes the benchmark only 0.25x as fast. However, we're hopeful that in more moderate usage this will not be a significant issue. Any help speeding up
@asamuzakjp/dom-selectoris appreciated, and feel free to open an issue if this has had a significant impact on your project.v23.1.0Compare Source
ElementInternals, including theshadowRootgetter and the string-valued ARIA properties. (zjffun)Element.history.pushState()andhistory.replaceState()to follow the latest specification, notably with regards to how they handle empty string inputs and what new URLs are possible.input.valueAsANumbersetter to handleNaNcorrectly. (alexandertrefz)cssstylewhich contains several bug fixes.v23.0.1Compare Source
canvaspeer dependency introduced in v23.0.0.v23.0.0Compare Source
whatwg-urlwhich integrates various additions to theURLandURLSearchParamsobjects.Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.